Multidomain, intercarrier network-to-network interface

ABSTRACT

A method, system, and network-to-network interface are provided for sharing data across networks in different domains. An embodiment of the method includes receiving from a requesting device a request for services by way of a first network in a wireless-communications-services (or other) domain; determining that the request requires information in a second network in a cable-television-services (or other) domain; retrieving the information from the cable-television-services domain; and communicating the retrieved information to the requesting device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of three U.S. ProvisionalApplications (all of which are incorporated by reference herein): 1)Application No. 60/864,340 filed Nov. 3, 2006; 2) Application No.60/853,307 having a filing date of Sep. 29, 2006, entitled “CASCADINGNETWORK LOGIN”; and 3) Application No. 60/853,306 also having a filingdate of Sep. 29, 2006, entitled “MULTIDOMAIN, INTERCARRIER,NETWORK-TO-NETWORK INTERFACE”.

Moreover, Applicants wish to call the Office's attention to the factthat the five following Applications (one of which is this one), filedon even date herewith, include related disclosed subject matter: 1)“DYNAMIC CSCF ASSIGNMENT”; 2) “NAI (NETWORK ACCESS IDENTIFIER)EMBEDDING”; 3) “EXTRACTING EMBEDDED NAIS (NETWORK ACCESS IDENTIFIERS)”;4) “MULTIDOMAIN, INTERCARRIER, NETWORK-TO-NETWORK INTERFACE”; and 5)“CASCADING NETWORK LOGIN”. The subject matter of each of these documentsis expressly incorporated by reference herein.

BACKGROUND

In the past, data providers of a first domain have maintained a highdegree of separation from data providers of a second domain. Considertwo illustrative examples: the “cable domain” and the “wireless domain.”Services in the “cable domain” are services provided by an entity whoprincipally owns or controls a cable TV (CATV) infrastructure.Illustrative services include television programming (includingsatellite, on-demand etc.), a form of high-speed Internet access, and avariety of other services. Providers in the “wireless domain”principally own or operate a large-scale wireless-communicationsnetwork. Illustrative services include mobile-phone communications,messaging (text, MMS etc.), other forms of Internet access, and more.Historically, there has been no need to consider resource sharingbetween those in the wireless domain and those in the cable domainbecause the respective services were sufficiently distinct, andrespective endpoints took on very different forms. For example, a cablebox of the 1980s bore little in common with a cell phone of that timeframe. But times are changing.

Today's and future smart phones, powerful PDAs, and other hybridelectronic devices will be able to do things that past dedicated devicescould not. For instance, a mobile-phone presents a version of televisionon its small display as long as the service is being provided by thesame carrier that provides voice service. Similarly, a cable company'sinfrastructure can be used by a cable company to offer telephoneservice, (e.g., via VoIP and a phone adapter) but again, as long as thecable company uses its resources to all the services to work.

The current state of the art could be improved by providing a frameworkin the form of one or more network-to-network interfaces that wouldallow the services of a first carrier or in a first domain to be able tobe used along with those of a second carrier or entity in a seconddomain.

SUMMARY

The presenting invention is defined by the claims below. Embodiments ofthe present invention solve at least the above problems by providing asystem and method for, among other things, sharing infrastructureresources across networks in different domains. The present inventionhas several practical applications in the technical arts includingallowing a customer of a company in a first domain to be able to utilizethe services of another (of the same) company in another domain.

In a first illustrative aspect, a network-to-network interface embodiedin one or more computer-readable media are provided for facilitating amethod of sharing data across networks in different domains. The methodincludes receiving from a requesting device a request for services byway of a first network in a wireless-communications-services domain,determining that the request requires information in a second network ina cable-television-services domain, retrieving the information from thecable-television-services domain, and communicating the retrievedinformation to the requesting device.

In another illustrative aspect, a method includes receiving from arequesting device a request for services by way of a first network in acable-television-services domain, determining that the request requiresinformation in a second network in a wireless-communications-servicesdomain, retrieving the information from thewireless-communications-services domain, and communicating the retrievedinformation to the requesting device.

In a final illustrative aspect, a method includes receiving from arequesting device a request for services by way of a first network in afirst domain, determining that the request requires information in oneor more networks in one or more domains, and communicatively couplingthe requesting device to the one or more networks in the one or moredomains so that the request may be serviced.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the attached drawing figures, which areincorporated by reference herein and wherein:

FIG. 1 is a block diagram depicting an illustrative operatingenvironment suitable for practicing an embodiment of the presentinvention;

FIGS. 2 and 2A provide another depiction of an illustrative operatingenvironment suitable for practicing an embodiment of the presentinvention;

FIG. 3 is a combination block/process diagram depicting an illustrativeembodiment for cascading a login process from one domain to otherdomains according to an embodiment of the present invention;

FIG. 4 depicts various illustrative signaling types used to communicateacross various elements in connection with facilitating a cascadinglogin process according to an embodiment of the present invention; and

FIG. 5 is a call-flow diagram that depicts illustrative data exchangesthat facilitate a cascading log-in process according to an embodiment ofthe present invention.

DETAILED DESCRIPTION

Throughout the description of the present invention, several acronymsand shorthand notations are used to aid the understanding of certainconcepts pertaining to the associated system and services. Theseacronyms and shorthand notations are solely intended for the purpose ofproviding an easy methodology of communicating the ideas expressedherein and are in no way meant to limit the scope of the presentinvention. The following is a list of these acronyms:

AP Application Protocol AS Application Server BSC Base StationController BSS Business Support Systems (or Services) BTS BaseTransceiver Station CATV Cable TV CDMA Code Division Multiple AccessCD-ROM Compact Disk Read Only Memory CMS Call Management Server CMTSCable Modem Termination System CSCF Call Session Control Function DHCPDynamic Host Configuration Protocol DVD Digital Versatile Discs EEPROMElectrically Erasable Programmable Read Only Memory GLMS Group ListManagement Server GSM Global System for Mobile Communications GPRSGeneral Packet Radio Service HLR Home Location Register HSS HomeSubscriber Server I-CSCF Interrogating Call Session Control Function IMSIP Multimedia Subsystem IPR IP Rights LAN Local Access Network MMSMultimedia Messaging Service MSC Mobile Switching Center MTA MessageTransfer Architecture NNI Network-Node Interface OSS Operational SupportSystems (or Services) PCMM Packet Cable Multi Media PCRF Policy andCharging Resource Function P-CSCF Proxy Call Session Control FunctionPDA Personal Digital Assistant PDSN/HA Packet Data Serving Node/HomeAgent P/I-CSCF Proxy/Interrogating Call Session Control Function RAMRandom Access Memory RNC Radio Network Controller ROM Read Only MemorySCIM Service Capability Interaction Manager S-CSCF Serving Call SessionControl Function SIP Session Initiation Protocol TDMA Time DivisionMultiple Access VCC Voice Call Continuity VoIP Voice over InternetPacket VOP Voice Over Packet

Further, various technical terms are used throughout this description. Adefinition of such terms can be found in Newton's Telecom Dictionary byH. Newton, 21^(st) Edition (2005). These definitions are intended toprovide a clearer understanding of the ideas disclosed herein but arenot intended to limit the scope of the present invention. Thedefinitions and terms should be interpreted broadly and liberally to theextent allowed the meaning of the words offered in the above-citedreference.

Embodiments of the present invention may be embodied as, among otherthings: a method, system, or computer-program product. Accordingly, theembodiments may take the form of a hardware embodiment, a softwareembodiment, or an embodiment combining software and hardware. In oneembodiment, the present invention takes the form of a computer-programproduct that includes computer-useable instructions embodied on one ormore computer-readable media.

Computer-readable media include both volatile and nonvolatile media,removable and nonremovable media, and contemplates media readable by adatabase, a switch, and various other network devices. Network switches,routers, and related components are conventional in nature, as are meansof communicating with the same. By way of example, and not limitation,computer-readable media comprise computer-storage media andcommunications media.

Computer-storage media, or machine-readable media, include mediaimplemented in any method or technology for storing information.Examples of stored information include computer-useable instructions,data structures, program modules, and other data representations.Computer-storage media include, but are not limited to RAM, ROM, EEPROM,flash memory or other memory technology, CD-ROM, digital versatile discs(DVD), holographic media or other optical disc storage, magneticcassettes, magnetic tape, magnetic disk storage, and other magneticstorage devices. These memory components can store data momentarily,temporarily, or permanently.

Communications media typically store computer-useableinstructions—including data structures and program modules—in amodulated data signal. The term “modulated data signal” refers to apropagated signal that has one or more of its characteristics set orchanged to encode information in the signal. An exemplary modulated datasignal includes a carrier wave or other transport mechanism.Communications media include any information-delivery media. By way ofexample but not limitation, communications media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, infrared, radio, microwave, spread-spectrum, and otherwireless media technologies. Combinations of the above are includedwithin the scope of computer-readable media.

FIG. 1 depicts an illustrative environment 110 where services have thetechnical capability to be exhibit shared relationships with each othereven though services are being provided by different (as opposed to thesame) carriers. A converged services environment 110 allows services ineither domain to be provided to a customer without the customer knowingthat such services are being provided by different entities (or the sameentities in different domains). In an illustrative example, a userwatching a certain television channel, say PBS, may be in the middle ofwatching a show on the television but can now have that show sent to hisor her mobile device (phone, PDA, etc.) to finish after they have leftthe living room (while taking a taxi cab to the airport for example).

In one embodiment, the architecture described herein leverages IMS, orIP

Multimedia Subsystem technology, taking its principles further. An IPMultimedia Subsystem (IMS) network is a standardized architecture fortelecom operators who want to provide mobile, fixed multimedia, andother services. It supports a Voice-over-Packet (VoP) implementationbased on a 3GPP standardized implementation of SIP that can run over thestandard Internet Protocol (IP). Existing phone systems (bothpacket-switched and circuit-switched) can be supported.

IMS uses open standard IP protocols, defined by the IETF (InternetEngineering Task Force). A multimedia session between two IMS users,between an IMS user and a user on the Internet, and between two users onthe Internet is established using the same protocol. Moreover, theinterfaces for service developers can also be based on IP protocols.This is why IMS can facilitate merging the Internet, CATV, cellular(mobile) communications, and more.

Although IMS allows some convergence of services (such as voicemessaging and voice), it is constrained in that it can facilitate suchservices offered only by a single provider. Thus, a first carrier mayuse IMS to send television to a mobile phone using IMS only if thattelevision stream is provided by said first carrier, which is a verydifferent scenario than, say, said first carrier allowing a subscriberto watch television programming provided by a second carrier, which iswhat an embodiment of the present invention allows.

Thus, IMS has been defined as if all the services are residing in oneenvironment under one ownership and to be delivered to endpointsassociated with that environment. Mobile carriers control their mobileend points (handheld devices), but when the customer enters into thecable environment (his or her home for example), they lose control overthat customer because digital phone and entertainment services are allprovided by an entity in a different domain, such as a cable provider.

One applicable environment suitable for practicing an embodiment of thepresent invention includes that where each entity has their own IMSstructure. An embodiment of the present invention allows the twonetworks to interwork so that services historically delivered only viatheir respective IMS infrastructures can be shared in a way that theservices can be collectively and transparently delivered to customers.

In this way, an appropriately equipped handheld device can utilizewireless technologies (such as CDMA, TDMA, GPRS, GSM, etc.) when awayfrom home or other localized areas, but use wireless LAN technologieswhen in the vicinity of a wireless LAN (e.g., airports, homes,bookstores, and wherever else a WiFi or similar connection can beutilized).

Returning to FIG. 1, a network-to-network interface (NNI) 112 exposesthe resources of a first carrier in a first domain 114 with those of asecond carrier in a second domain 116. Various clouds are shown thatillustratively represent various services offered by each carrier. Byway of example, cloud 118 includes technologies related to determiningand utilizing presence information. Presence information relates toinformation associated with a geographic location or designated statusof a person. One example includes emoticons (sometimes called “smileyfaces”) that indicate whether people are away from their computer, orsleeping, or otherwise unavailable. Presence information can also conveyactual geographic location of users, via the location of their handhelddevices. This is useful in providing location-based services and, insome scenarios, can be used to facilitate or help facilitate sessionhand off when one transitions from home to beyond.

Illustrative components that may be employed to provide presenceinformation includes a Group List Management Server (GLMS), a Parlay orsimilar client (also know as a Parlay X Web service), or otherApplication Server (AS). Similar presence information is shown in cloud120 associated with second domain 116.

Cloud 122 also depicts illustrative components that might be included,such as a Service Capability Interaction Manager (SCIM), a Policy andCharging Resource Function (PCRF), a Home Subscriber Server (HSS), aProxy Call Session Control Function (P-CSCF), a Serving Call SessionControl Function (S-CSCF), and an Interrogating Call Session ControlFunction (I-CSCF). These components are illustratively shown also incloud 124, associated with second domain 116.

Cloud 126 depicts illustrative communications components including aBase Station Controller (BSC), a Radio Network Controller (RNC), a HomeLocation Register (HLR), a Base Transceiver Station (BTS), a MobileSwitching Center (MSC), and a Packet Data Serving Node/Home Agent(PDSN/HA).

In sister cloud 128, the following illustrative communicationscomponents are shown: a Cable Modem Termination System (CMTS), a MessageTransfer Architecture (MTA), a Packet Cable Multi Media component(PCMM), and a Call Management Server (CMS). Of course there may actuallybe many instances of such components.

NNI 112 makes possible the sharing of network resources across networksto various devices, such as a mobile device (handheld, PDA, and thelike) 130, a computer 132, and a television or equivalent 134. Roamingis thus possible, and can be done so seamlessly and transparent to auser, as indicated by line 136. Accordingly devices 130A, 132A, and 134Amay be the same devices as 130, 132, and 134, but in a differentlocation or operating using a different technology. For example,communications link 138 may be a wireless LAN link (e.g., one thatcomports with a variation of the 802.11 standard, such as 802.11a,802.11b, 802.11g, 802.11n, or others), whereas communication link 140may be a mobile wireless technology (e.g., CDMA, TDMA, GPRS, GSMC,etc.). This aspect is also explained in connection with FIG. 2 below.

NNI 112 may include various components that facilitate interoperabilitybetween the technologies of first domain 114 and those of second domain116. Due to space consideration on the drawing, FIG. 1 includes onlywords inside of NNI 112, but it is to be understood that each titledescribes a component that facilitates an aspect of interoperabilityfunctionality. The illustrative components include a policy-managementcomponent 142, a security-management component 144, aservices-interworking component 146, a session-control-interworkingcomponent 148, a service-roaming component 150, acustomer-profile-management component 152, a mobility-managementcomponent 154, a data-federation component 156, an IP address managementcomponent 158, a protocol-interoperability component 160, and a BSS/OSS(Business Support Systems/Operational Support Systems) interworkingcomponent 162.

Some of the aforementioned components may be implemented in hardware,software, or a combination of the same. They may be composed of severalconstituent components. Moreover, others may attribute different namesto the same components. Thus, descriptive adjectives have been providedthat indicate the functions that these various components carry out.Additional explanations of the same follow.

Policy-management component 142 enables policies to be shared among twonetworks or more networks. Throughout this disclosure, explanation isgenerally provided with respect to two networks. But the same teachingsdescribed herein can be applied to environments with more than twonetworks so that the resources of as many networks as are desired can beshared. But so as to not obscure the present invention, references totwo networks will be made, simplifying an explanation of but oneembodiment of the present invention or an aspect thereof. Both IMSdomains 114 and 116 include a policy-management architecture in oneembodiment that would include a master-policy server and multipledistributed slave policy managers.

Accordingly, the policies applicable to a subscriber associated with afirst domain, such as domain 114 can be commensurately effective in asecond domain such as domain 116. The part of NNI 112 between the twonetwork's master-policy managers may allow policy information about acustomer to be shared between two networks in one embodiment. Thissharing may include static as well as dynamic information. Staticinformation may be shared at the time of user registration in oneembodiment. Illustrative examples of static information include a userID (in one embodiment, it could vary in others), services the usersubscribes to, etc. Dynamic information may be shared at the time ofservice initiation in one embodiment. Illustrative examples of dynamicinformation include information that changes. This could include“cookie” type information but a better example may be presenceinformation as services may change based on location. Dynamicinformation may also include things such as the flow type (VoIP=highQoS, Internet traffic=best effort, etc.). The user profile mayover-write a dynamic parameter with a static value if the user profilechanges (i.e., raises QoS to Gold level regardless of traffic flow type)a dynamic parameter to a predefined value.

Security-management 144 provides security interfaces between thenetworks so that the specific network topologies may be hidden from eachother if desired. Although certain aspects or resources of each networkmay be desired to be shared as though the networks are one network, inthe situations where, in fact, they are not one network, it may bedesirable to keep other aspects of each network private.

Services-interworking component 146 allows services from multipledomains to be delivered to a customer irrespective of which domain theyare connected to at any given point. It allows the available services tobe published to a customer's device (e.g., one or more of 130, 132, or134). In one embodiment, the serving IMS network has the responsibilityto poll the other IMS domains to discover what services are availableacross all the IMS domains.

Session-control-interworking component 148 allows the serving networkdomain (where the user is at any given point) to control the sessionsand services for the customer. This is an advance over the current stateof the art, wherein current IMS architecture allows only the homenetwork to control sessions and services.

Service-roaming component 150 facilitates cross-domain roaming. In thissituation, a customer roams from one IMS domain (such as 114) to others(such as 116), triggering new registration to the other network as thecase may be. The second network 116 then interacts with the home network114 to gather customer information such as profile, policy, subscribedservices, etc. Through the interfaces with other IMS domains, suchservices may be delivered.

Customer-profile-management component 152 manages sharing of informationof customers' profiles across multiple networks. In one embodiment,customer-profile data may be stored as an HSS (Home Subscriber Server)network element (see reference numeral 214, FIG. 2 for example). Whenthe customer is first provisioned, the subscriber information isprovisioned in the HSS, such as 214. In the multidomain architectureaccording to an embodiment of the present invention, when the subscriberis provisioned in one operator's HSS 214, the interface between HSSs(e.g., between HSS 214 and HSS 216) allows that provisioning informationto be passed along to other HSSs so that a subscriber is provisioned tomultiple IMS networks at the same time. Depending on the amount ofprivacy desired, a roaming partner may not necessarily receive theentire user profile in some embodiments. But some portion of the profile(or domain) information may be shared in order to allow users toauthenticate in visited domains as part of the roaming agreement is suchis desired.

Seamless-mobility-management component 154 allows the user to move fromone network to the other network while maintaining services withoutservice interruption. Applicable technologies for such handoff andmaintenance include voice, chat, messaging, video, and more. A VoiceCall Continuity (VCC) server (not shown) can maintain call state whenthe user moves from one access network 114 to the other access network116. To facilitate such continuity in a multidomain environment,multiple VCC implementations (for example, one per each domain) can beemployed in one embodiment. As the user moves from one domain 114 to theother domain 116, the visiting IMS network 116 would connect thatsession back to the originating IMS network 114 while the active call isongoing. When the user enters an idle state (e.g., not in an activecall), the client in the device would change the VCC server to the newIMS network 116.

Data federation component 156 facilitates operations associated withdata federation, such as integrating diverse data in an enterprise orother environment. Other examples include resolving issues associatedwith transparency, heterogeneity, autonomy, and extensibility. Datafederation component 156 allows intra-session inter-working of servicesand functions residing in multiple independent IMS infrastructures.

IP-address-management component 158 manages IP addresses across domains.In a multidomain environment, the IP address is assigned by the networkthat the user is connected to at any given point in one embodiment. Asusers move from one network 114 to another network 116, they may need toor it may be desirable to change their respective IP addresses. The IPaddress may be bound to several services that the customer is receiving.But changing an IP address could mean that the user would need toreregister with the network, causing a service interruption.IP-address-management component 158 helps communicateaddress-information change in a way that each network can still maintaina servicing state while the user changes networks until the userderegisters himself (e.g., by turning off the phone).

Protocol-interoperability component 160 translates data transmitted inprotocol into that of another in instances where the networks indifferent domains communicate in disparate protocols in one embodiment.In another embodiment, a standard protocol is used, and allcommunications are translated according to that selected protocol.

BSS/OSS-interworking component 162 allows for the facilitation ofbusiness support services and operational support services.

Turning now to FIG. 2, another illustrative operating environmentsuitable for practicing an embodiment of the present invention isprovided and referenced generally by the numeral 200. A first carrier ornetwork of a first domain 210 is depicted along with a second currier ornetwork in a second domain 212. Coupled together by a network-to-networkinterface (NNI) 218, which could be the same as NNI 112 of FIG. 1. Firstdomain 210 may, for example, be a domain associated with a wirelesscarrier that provides wireless connectivity to such devices as a mobilephone, mobile email device, PDA, etc. (collectively and illustrativelyrepresented by device 220). A call session control function (CSCF)component is referenced by the numeral 222. It is coupled to a homesubscriber's server (HSS) 214, which provides access to one or moredatabases 224 that store profile data associated with customers. Profiledata stored in database 224 may relate to billing data, preference data,device-type data, and the like.

CSCF 222 is also coupled to one or more application servers 226.Application servers 226 may provide a variety of functions. For example,an illustrative application server may provide voice functionality. Thatis, the ability to have a voice telephone call between two (or more)entities. Another illustrative application that may be provided by anapplication server includes facilitating chat sessions. Otherillustrative applications that could be provided include text messaging,multimedia messaging, videoconferencing, Internet access, and the like.In one embodiment, device 220 communicates with CSCF 222 via mobilewireless technologies, such as CDMA, TDMA, GSMC, GPRS and the like,illustratively represented by cloud 228.

In another setting, such as when device 220 enters second domain 212,(referenced by numeral 220A for clarity, it is contemplated to be thesame device as 220), it communicates via a wireless technology such as awireless LAN 230 with a box 232. Wireless LAN 230 may operate with avariety of protocols. Demonstrative protocols include variations of the802.11 format, such as 802.11a, 802.11b, 802.11g, 802.11n, and the like.Box 232 is represented in generic fashion and may actually correspond tomultiple constituent devices.

For example, box 232 may be a cable set-top box (or integratedcircuitry) equipped with wireless-access-point functionality.Alternatively, box 232 may represent a wireless access point (such as awireless router) coupled to a cable modem, which, through a portion ofcable infrastructure (represented by numeral 234) is coupled to aservices provider 236. Services provider, or services interface, 236 isalso coupled to a variety of application servers referenced generally bythe numeral 238. Historically, these services would have beeninaccessible to subscribing device 220. But by virtue of NNI 218, theycan be made available to device 220.

Various applications provided by an application server or variationthereof 238 include cable-television (or other content-type) delivery,voice over packet (VOP, e.g., VoIP) communications, and a variety ofothers. Services provider 238 is coupled to HSS 216 in domain 212, whichexposes a set of profiles 240. Thus, in one embodiment, a customer of acable provider, which may be in domain 212, may have a first profile asone of the profiles maintained in one or more databases 240. That samecustomer may have an account with a wireless carrier, and thus haveprofile data stored in one or more databases 224. But by virtue of NNI218, mobile device 220 can communicate with the profiles stored indatabases 240 to determine what type of services associated with secondcarrier 212 may be permissibly deliverable to device 220.

An HSS to HSS NNI may require strict policies and processes in oneembodiment. Appropriate authorization for information to flow betweendomains will be provided, as explicit profile information may staywithin the primary service domain in an embodiment. Users might requestthat profile information be shared between domains to enable new and/orunique services.

The type of services deliverable may turn on the type of device that 220is, or the functionality it is capable of providing (such as videorendering, MMS capabilities, etc.) or it may turn on subscribinginformation. For example, if a person subscribes to a premium tier ofcable TV offering, such as premium channels, then such content would bedeliverable to device 220. But if the same customer subscribed only tobasic cable, then content associated only with those channels may bestreamed to device 220. In this way, seamless roaming between firstcarrier 210 and second carrier 212 would be facilitated by NNI 218.

If users are using a wireless LAN network 230 in their homes, and thecable modem connection for all their cable services, when they gooutside the home, NNI 218 can facilitate data communication via CDMA orother mobile phone technology 228 so that the end device 220A continuesto receive service uninterrupted. Device 220A becomes one common devicefor data services, but services can operate with other end devices suchas a television and PC (as shown in FIG. 1). A customer would not evenknow nor need to know which technology is being utilized to effect thecurrent service offering.

NNI 218 facilitates the sharing of information that is required todeliver services across these two environments 210 and 212 such thatwhen a customer is in a certain location and requesting certainservices, it can request anything in any domain that it has access to.These services can be managed as the customer moves around.

In this cross-domain environment, services from either one of thedomains can be delivered anywhere. The architecture allows these twodomains to exchange all the information that is necessary. To thecustomer, and to certain endpoints or other devices, rather thancommunicating with a respective CSCF 222 or its correspondingcounterpart in second domain 212 (which could be another CSCF orequivalent, such as services component 236), both devices are seen as acommon device, a situation graphically shown by dashed line 242 in FIG.2A. Device 220 or 220A would not even know that it is requestingservices of one domain versus another, just that it is requesting acertain type of service, and that request would be granted.

Cascading IMS Login

In one embodiment, this aspect of the invention provides a mechanism bywhich an owner of a first IMS system may allow IMS subscribersconnecting though one IMS domain to access services on another (e.g., aremote) IMS domain without additional functionality needing to be addedto subscriber equipment. This aspect relates to providingsession-control interworking 148. When the subscriber is usingconnectivity provided by a first entity, the automated cascading IMSlogin process allows a local Serving-CSCF (S-CSCF) of the first entityto act as a proxy or Interogating-CSCF/CI-CSCF. The S-CSCF usesinformation retrieved from the first entity's HSS to login to a secondentity's IMS domain. In one embodiment, the session initiation protocol(SIP) is leveraged along with additional RADIUS/DIAMETER parameters.Among other things, this aspect of the invention facilitates thereaching of roaming user access to services on the IMS domain of boththe original and roaming service provider's applications and services,thereby allowing simultaneous reachability of IMS services betweenmultiple domains by subscribers.

Turning now to FIG. 3, an illustrative method for allowing an IMS loginto be automatically cascaded from a first domain to other domainsaccording to an embodiment of the invention is provided and referencedgenerally by the numeral 300. To have a login automatically cascadedfrom a first domain to another or more domains means to substantiallymake it as though a user had logged into the second or more networks.That is, so that at least a portion (or even all) services that would beavailable to customers logged in to the second network will also beavailable to the customers who first logged into a first network, andhad such login information utilized to register with the second network.

FIG. 3 depicts a handheld device 310 and also an IMS in a first domain312, an IMS in a second domain 314, an IMS in a third domain 316, and anIMS in a fourth domain 318. Additional domains could be added of course,but those that are shown are for explanatory purposes and areillustrative in nature. Also shown in their respected domains are firstHSS 320 and first S-CSCF 322 associated with first domain 312; secondHSS 324 and second S-CSCF 326 associated with second domain 314; thirdHSS 328 and third S-CSCF 330 associated with third domain 316; andfourth HSS 332 and fourth S-CSCF 334 associated with fourth domain 318.

Out of step 340, handset 310 becomes aware of and starts to facilitate afirst IMS registration with first S-CSCF 322 in first domain 312. Firstdomain 312 in this example may be a person's wireless carrier forexample. Out of step 342, first S-CSCF 322 in local domain 312automatically cascades an IMS login to second S-CSCF 326 based on valuesreturned from its local HSS 320.

An illustrative example is indicated by numeral 344, whichillustratively shows that any additional IMS logins can be automaticallycascaded to any number of domains. For example, first S-CSCF 322 alsoautomatically cascades and facilitates the login process with thirdS-CSCF 330 in third domain 316 based on the values received from thelocal HSS 320 in first domain 312.

Though not required, it may be the case that logins may not be cascadedpast one level. For example, out of step 346, suppose that S-CSCF 326attempted to further cascade a login from first domain 312 onto fourthdomain 318 by communicating with fourth S-CSCF 334. To the extent thisis undesirable, an “X” denoted by reference numeral 346 illustrates thatonly the S-CSCF 322 in first domain 312 is allowed to perform cascadingIMS login. But if such subsequent cascading login was desired, then thesame could be allowed. With the IMS logins automatically cascaded downto second domain 314 and third domain 316, device 310 may now access theservices associated with the HSS components in the respective domains.Device 310 may access services exposed by HSS 324 and second domain 314as well as services exposed by HSS 328 and third domain 316. This can beused to share access to profile data stored in profile databasesassociated with the HSS components or be used to help facilitateservices provided by one or more application servers via the respectiveCSCF in each domain.

FIG. 4 depicts illustrative signaling in an environment where a homeS-CSCF is acting as a P-CSCF to facilitate a single-login scenario. Asshown, SIP signaling is depicted by a line having the style of thatrepresented by reference numeral 410, policy signaling having formatindicated by reference numeral 412, and session-negotiation signalinghaving a line type as indicated by reference numeral 414. FIG. 4, aswith all FIGs, is incorporated by reference into the specification ofthis patent application and clearly indicates diagrammatically whatwould take many words to describe, but not necessarily explain in anyclearer detail. Similarly, FIG. 4 illustrates but one example of anembodiment that utilizes various kinds of signaling types and/orprotocols across various devices. Other types of signaling could beemployed to communicate across the various devices shown in FIG. 4, aswhat is shown is done so to illustrate an aspect of the invention andprovide one example of an embodiment that utilizes the various signalingtypes and protocols shown.

Turning now to FIG. 5, a call flow diagram represents illustrativeexchanges of information between components in a local IMS 510 (firstdomain) and components in a remote IMS 512 (second domain). Exemplarydevices associated with local IMS domain 510 include a mobile network514, a P/I-CSCF 516, a local HSS, and an S-CSCF 520. Exemplary devicesshown associated with remote IMS domain 512 include a remote HSS 522 anda remote S-CSCF 524.

At a step 550, a handset sends a SIP registration to local P/I-CSCF 516that may be, for example, resolved through DHCP or other mechanisms. Ata step 552, proxy and interrogating CSCF 516 queries for a local servingCSCF from local home subscriber service 518.

At a step 554, local Home Subscriber Server 518 assigns an S-CSCF forthis user's session. At a step 556, P/I-CSCF 516 sends a SIPregistration to local S-CSCF 520, which facilitates a Cx-putcommunication to local HSS 518 to obtain subscriber-specificinformation. S-CSCF 520 requests cascading IMS login information.

At a step 560, local HSS 518 responds with subscriber-sessioninformation as well as information supporting a cascading IMS login.Illustrative information supporting a cascading IMS login includesidentifying indicia associated with the destination HSS system name(such as a logical name or IP address) to identify informationassociated with a destination domain that might be private.

At a step 562, S-CSCF 520 of local IMS domain 510 acts as a P/I-CSCF byquerying the remote HSS 522 for information relating to target S-CSCF524 and remote IMS domain 512. At a step 564, remote HSS 522 replies tothe query with information describing the target S-CSCF 524. At a step566, local S-CSCF 520 performs service control, and the subscriber isactivated on local IMS domain services.

At a step 568, local S-CSCF 520 sends a SIP “200 OK” message to P/I-CSCF516 indicating a successful connection to local IMS services. Of courseif a different protocol were being used besides SIP, an analogousmessage could be sent according to the specific protocol employed. At astep 570, the message at the previous step is forwarded on to the IMSclient on the local device via mobile network 514.

To facilitate cascading IMS login, local S-CSCF 520 sends a registeredmessage to remote IMS domain 512 on behalf of a mobile device. Theregister message contains the private user identity IMS system that wassupplied to local S-CSCF in step 560 in one embodiment. At a step 574,remote S-CSCF 524 communicates a Cx-put message to remote HSS 522 togather subscriber-specific information. S-CSCF 524 does not need torequest cascading IMS information in one embodiment.

At a step 576, remote HSS 522 replies with the requestedsubscriber-session information. At a step 578, an ‘OK” message is sentby remote S-CSCF 524 to local S-CSCF 520 to facilitate IMS registrationon remote IMS domain 510. At a step 580, remote S-CSCF 524 performsremote service control, and the subscriber is activated on remote IMSdomain 512, making its services available to a mobile device.

The call-flow steps illustrated in FIG. 5 are not to be construed asexact steps, each of which that need to be performed and/or in aspecific order, but is meant to illustrate one example of effectingsimultaneous reachability of IMS services between multiple domains by awireless subscriber according to an embodiment of the present invention.As mentioned, if different protocols are employed, then different typesof messages will be sent, but the overarching act of automaticallyregistering with a remote IMS on behalf of a mobile device will becarried out.

Many different arrangements of the various components depicted, as wellas components not shown, are possible without departing from the spiritand scope of the present invention. Embodiments of the present inventionhave been described with the intent to be illustrative rather thanrestrictive. Alternative embodiments will become apparent to thoseskilled in the art that do not depart from its scope. A skilled artisanmay develop alternative means of implementing the aforementionedimprovements without departing from the scope of the present invention.

It will be understood that certain features and subcombinations are ofutility and may be employed without reference to other features andsubcombinations and are contemplated within the scope of the claims. Notall steps listed in the various figures need be carried out in thespecific order described.

The invention claimed is:
 1. One or more nontransitory computer-storagemedia having computer-executable instructions embodied thereon that,when executed, implement a network-to-network interface for facilitatinga method of sharing data across networks in different domains, themethod comprising: providing to a requesting device, in a first networkin a wireless-communications-services domain, access to profile data ina second network in a cable-television-services domain, wherein theprofile data includes an indication of a cable service to which therequesting device subscribes; receiving from the requesting device arequest for the cable service by way of the first network; determiningthat the request requires information in the second network in thecable-television-services domain; retrieving the information from thecable-television-services domain; by way of a session in the firstnetwork communicating the retrieved information to the requestingdevice; determining that the requesting device has moved from the firstnetwork to a wireless local-area network (WLAN); and seamlesslycommunicating the retrieved information by way of the WLAN to therequesting device, wherein the session is connected back to the firstnetwork while the session remains active, and wherein the session isswitched to the WLAN during an idle state.
 2. The media of claim 1,wherein the requesting device includes a handheld device capable offacilitating a voice call.
 3. The media of claim 1, wherein the requestfor the cable service includes a request for receipt of television-typeprogramming.
 4. The media of claim 3, wherein the television-typeprogramming includes real-time or previously recorded content.
 5. Themedia of claim 3, wherein the television-type programming includes oneor more of: an advertisement; a pay-per-view show; a voice-over-packetcommunication; and access to at least a portion of the Internet.
 6. Themedia of claim 5, wherein the voice-over-packet communications includesVoice over Internet Packet (VoIP).
 7. The media of claim 1, wherein thefirst network is substantially owned by a first company, but the secondnetwork is substantially owned by a second company.
 8. The media ofclaim 1, wherein the first network principally employs a first type ofcommunications protocol, but the second network principally employs asecond type of communications protocol.
 9. One or more non-transitorycomputer-storage media having computer-useable instructions embodiedthereon for facilitating a method of sharing data across networks indifferent domains, the method comprising: receiving a request forservices by way of a first network in a cable-television-services domainfrom a requesting device; determining that the request requiresinformation in a second network in a wireless-communications-servicesdomain; retrieving the information from thewireless-communications-services domain; and by way of a session in thefirst network communicating the retrieved information to the requestingdevice; determining that the requesting device has moved from the firstnetwork to a third network, wherein the first network principallyemploys a first type of communications protocol and the third networkprincipally employs a second type of communications protocol; andseamlessly communicating the retrieved information by way of the thirdnetwork to the requesting device, wherein the session is connected backto the first network while the session remains active, and wherein thesession is switched to the third network during an idle state.
 10. Themedia of claim 9, wherein the request received by way of the firstnetwork includes a request for content via the second network in thewireless-communications-services domain.